feat: process and prepare PECD capacity factor time series for offshore generators - #53
Conversation
…_renewable_profiles
…es and fix name of profiles in add_brownfield rule
… clean_pecd_data with handling of not available pecd years
…ded. Needs to be reverted later
…te download link for pecd data
…ween tyndp renewable carriers and pecd renewable profiles
…/49-pecd-offshore
…replace UK with GB naming convention
tgilon
left a comment
There was a problem hiding this comment.
Thank you, @daniel-rdt, for the updates. I'm happy with the current set of configuration levels. This is a good balance between redundancy and user-friendliness. I have a few minor comments below.
Co-authored-by: Thomas Gilon <thomas.gilon@openenergytransition.org>
There was a problem hiding this comment.
Hmm .. looks good.
The key thing i am wondering is more about where all the other characteristics of the tyndp renewable carriers are being defined. Think capacities, costs, ..., and whether profile then should not be a setting of that set of configuration items?
I am also wondering whether you can come up with a new name for the Tyndp technology name, ie. pecd_tech or tyndp_tech and then use that consistently to as variable names to differentiate between carrier and carrier :). It looks like in the config snippet suggestion you are using pecd_carrier for that.
Co-authored-by: Jonas Hörsch <coroa@posteo.de>
for more information, see https://pre-commit.ci
|
I just now quickly tried the PR from a clean slate. I am getting a This is understandable, because the whole tyndp bundle is only there after extraction. So this would have to be added to the output of |
for more information, see https://pre-commit.ci
…/49-pecd-offshore
…ected technologies and remove techs covered by TYNDP carriers from list
Good catch! Thanks @coroa. Curious that it most of the time ran through in the CIs still. Sometimes the retrieve timing works naturally and then there is no missing input, maybe the download speed is quicker on for the CI. Good to have the dependency fixed within Snakemake. |
…tus (#99) * doc: add more prominent disclaimer to README.md about development status * feat: add disclaimer to index file and include reference to dev status * feat: update limitations section to be specific to TYNDP and Open-TYNDP * feat: introduce overview of already implemented features and features in development * fix: fix see also in readme * fix: fix see also in readme (again) * feat: update feature table with PR links * feat: update feature table with separate PR column and new pending symbol * Apply suggestions from code review Co-authored-by: Thomas Gilon <thomas.gilon@openenergytransition.org> * fix: move PR #53 to pecd row in dev status table * fix: improve consistency in link to github issues * fix: remove emojis from readthedocs headers --------- Co-authored-by: Thomas Gilon <thomas.gilon@openenergytransition.org>
Closes #49. This PR is necessary for addressing #48.
Changes proposed in this Pull Request
This PR prepares the workflow to use PECD v3.1 data as input for renewable capacity factor time series of offshore generators. TYNDP generators are differentiated by their foundation type and offshore section type. This is described by their suffixes as described in the methodology report on p.47:
All TYNDP Offshore generator technologies use the same PECD profile
Offshore_Wind.The openly published TYNDP 2024 input data from PECD includes renewable time series for the years, 2030, 2040 and 2050.
To reproduce and test the implementation of this PR, you can run the 'Make' Rule:
To produce a
dagof the adapted workflow of this PR with PECD profiles instead of default atlite renewable profiles as specified in the configuration file, you can call:The PECD renewable profiles output files
resources/profile_pecd_{clusters}_{technology}.nchave the following structure:Tasks
Workflow
(new) retrieve rule:
retrieve_tyndp_pecd_datawhich downloads the TYNDP PECD data from Google Drive and extracts it in thedata/tyndp_2024_bundlesubdirectory. This rule will be deprecated once the data bundle has been updated ([PARENT] Update TYNDP 2024 data bundle on Zenodo #87).(new) configuration option
electricity/tyndp_renewable_profileswhere one can choose whether to use PECD renewable profiles and for which technologies. There on can specify both the PECD technology and the TYNDP renewable carriers associated to that profile. This two layer approach serves helpful to reduce the amount of processing required as multiple TYNDP renewable carriers use the same PECD profile (e.g. all offshore wind technologies).The PECD technology can be any of {
Wind_Offshore,Wind_Onshore,LFSolarPV}.The
tyndp_renewable_carriersare listed seperately to the already existingrenewable_carrierslist. Alltyndp_renewable_carrierslisted must also be mapped to a PECD technology and must not be included inestimate_renewable_capacitiestechnologies.Adapted inputs to rules
add_electricity,prepare_sector_networkandadd_brownfieldbased on this new setting(new) rule and script
clean_pecd_data(new) rule and script
build_renewable_profiles_pecdHotfix: In
add_existing_baseyearandadd_brownfieldskipped addition of existing renewables andp_max_purespectively for specified technologies that use pecd data until their TYNDP generator components are added to the systemOpen Issues
Notes
The updated workflow is described by the following simplified
dagshowcasing all the rules between theclean_pecd_datarules and thesolverules when callingsnakemake solve_sector_networks --configfile config/config.tyndp.yamlChecklist
envs/environment.yaml.config/config.default.yaml.doc/configtables/*.csv.config/test/*.yaml.doc/data_sources.rst.doc/release_notes.rstis added.